Static contact details contain a template-domain signal or narrow cross-page conflict
ShipReady found either a recognised template-domain email address or a limited static inconsistency between selected contact details on fetched pages.
Why it matters
Template detail or inconsistent public contact information warrants a review of the authoritative contact path.
How ShipReady detects it
What it inspects
ShipReady reads successfully fetched page text, selected route labels, email addresses, and tel links.
What triggers a finding
It reports a fixed template-domain email, or a narrow footer-versus-Company/Homepage email-domain conflict, or exactly one footer and one contact-page phone with different normalized final ten digits.
What the evidence shows
The evidence proves the reported static text matched one of those limited patterns.
Limits of this check
ShipReady does not query DNS, test mailbox delivery, verify ownership, determine which value is current, or infer intent. A template-domain match is not proof an address cannot receive mail.
Other contact methods, JavaScript-rendered content, and broad site consistency are outside this rule.
How to fix it
Review the observed evidence
Replace placeholders or reconcile the reported public values after identifying the authoritative detail.
How to verify the change
Verify the intended behavior
Review the affected routes and independently test the chosen contact channel.
Expected: The authoritative public details are consistent and the intended channel has been independently verified.