One of my sites came up as hacked on Google recently so I have been trying to fix the problem. When I looked at it using a browser, everything looked normal, but when I looked at it using "Fetch as Google" a load of junk came up after the first meta tag. I got rid of the spurious code by adding:
<http-equiv="x-dns-prefetch-control" content="off">
to the header, but my question is: Does anyone have any idea how this could have happened please? I am on an IIS server but when speaking to the host company (123-reg) they said that it was not possible for their server to be hacked. Has anyone else had this sort of problem?
I have fixed the issue on the surface but I am concerned with where the vulnerability lies.
Thanks in advance for any help with this matter.
Related
So, I've been working to improve the Lighthouse score on my site. In Best Practices it says there are Issues logged but I can't see any in the Issues panel.
Is there an issue with Lighthouse? Am I looking in the wrong place? I can't find any information about this online.
Link to the site:
https://wordpress-617059-2002059.cloudwaysapps.com/
Screenshots of the mention of Issues and the issues panel.
As per Graham's comment, should have checked the "include third-party cookie issues" to find them. Thanks again!
I don't seem to be able to post comments on my blog anymore.
The blog was put together by my predecessor at the company where I work using BlogEngine.
The error message says:
Value cannot be null.
Parameter name: challenge
I'm not sure what the cause is but I believe it has to do with the change of url of Google's recaptcha plugin. I've done some research on this and the address does seem to have changed.
Apologies if this is a bit vague, but I was wondering if anyone has experienced this issue with BlogEngine.
I'm not sure if you're facing the same issue but I had an issue with comments being posted on my blogengine blog where when you click on submit nothing happens. After a lot of digging it was a result of having the HTTP/axd compression settings turned on in blogengine.
You could try to play around with these and see if that makes a difference.
Cheers,
D
I have been building a site using basically html coding and have come stuck across a little problem that im sure somebody may be able to help me with.
The facebook comments box dosent seem to appear when i am trying to add the text shortcut to a site that ive created stored on a localfile. For example the site is called: file:///F:/GoogleMaps_FusionTables/WorkingCheckBox.html due to it being developed within a html file editor and not yet placed on a website.Is there anyway of getting this to test here before uploading it to a website server?
Any assistance or advice you could give would be greatly appreciated.
Many thanks,
Ian Usher
using a local web server will solve your problem.
Heya,
I'm using google api to access calendar data, and when I visit the site (djkstyles.com) I see the following:
http://cl.ly/2y2m3o3D0f0j1z0D0N03
But one some machines, this is what's seen:
http://cl.ly/292g2j3s341O2n3E020Y
It's really strange. The data coming through is consistent from Google; does anyone have any idas on what's up with this?
Thanks for any help.
Did a little bit more digging, and you're not alone: Calendar Issues Thread.
It seems that adding &hl=en to the end of your URLs should fix this. Like so: http://www.google.com/calendar/feeds/kbfj3n6iuc3u822d5omj06vt38%40group.calendar.google.com/public/basic?max-results=5&orderby=starttime&sortorder=ascending&callback=embedEvents&alt=json-in-script&futureevents=true&hl=en
I tried this and it fixed the raw data for me.
I am beginner in HTML and CSS. I just designed web site and tried to validate but my HTML end up having some "geovisit();"
and it wont validate.
I do not know how to get rid of it.
Help me?
Thank you
Guest
A quick Google search for geovisit suggests that the non-validating code is being added by your hosting provider. It looks like this problem may actually be specific to Yahoo!, which has an option to disable that "feature". I suggest you read this forum thread on the problem.
That's usually Yahoo (or other hosting providers) sticking javascript on your page without your knowing. In Yahoo's case you should be able to turn it off if you dig through the settings.